Merged
Conversation
Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Confirm gateway runs in routed mode and test tool exposure
Fix gateway default mode to routed
Jan 27, 2026
This was referenced Jan 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gateway was defaulting to unified mode when no
--routedor--unifiedflag was specified, contradicting documentation andrun.shbehavior.Changes
Fixed default mode: Changed
internal/cmd/root.goto default to routed mode instead of unifiedAdded tests: Verified non-existent tool call handling in both modes (
nonexistent_tool_logging_test.go)Tool Name Behavior
Confirmed and tested tool name exposure differs by mode:
/mcp/{serverID}"create-issue"/mcp"safeoutputs___create-issue"Non-existent tool calls properly return JSON-RPC errors and are logged via existing infrastructure.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
nonexistent.local/tmp/go-build98642035/b269/launcher.test /tmp/go-build98642035/b269/launcher.test -test.testlogfile=/tmp/go-build98642035/b269/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo --local x_amd64/vet user.email pVvZn2gawien(dns block)this-host-does-not-exist-12345.com/tmp/go-build98642035/b278/mcp.test /tmp/go-build98642035/b278/mcp.test -test.testlogfile=/tmp/go-build98642035/b278/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/c-test.run=TestNonExistentToolCallLogging jXVyRLCVa x_amd64/vet pull.rebase boring/sig(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.